Default: gn
Default: unset-retransmission-bit
Default: on-receiving-rule
This command configures whether to accept/reject CCA messages that contain Granted-Service-Unit AVP with only infinite quota grants from the server.
Default: reject-credit-control-answer
Use this command to accept/reject CCA messages that contain Granted-Service-Unit AVP with only infinite quota grants from the server.
The following command specifies to accept CCA with Granted-Service-Unit AVP containing only Infinite quota:
This command configures to accept/ignore rulebase ID in Rulebase-Id AVP returned by the Diameter server in CCA message.
This command enables to accept/ignore service ID in Service-Identifier AVP defined in the Diameter dictionaries. This command is applicable to all products that use the Gy interface.
Use this command to ignore/accept service ID value in Service-Identifier AVP in the Diameter dictionaries for Gy interface implementation.
This command can be used to disable the usage of Service-Identifier AVP for Gy interface implementation even if any of the Diameter dictionaries support Service-Identifier AVP and if this AVP should not be used for Gy interactions but instead should be present in GCDRs/eGCDRs.
Important: This command is available only in 10.2 and later releases.Default: Same as diameter mscc-final-unit-action terminate category
This command configures sending single/multiple Multiple-Services-Credit-Control (MSCC) AVP in CCR-U messages.
Important: This command is available only in 8.3 and later releases.Default: multiple
Specifies sending multiple Multiple-Services-Credit-Control AVP in a single CCR-U message.
Specifies sending only one Multiple-Services-Credit-Control AVP in a CCR-U message.
Use this command to configure sending single/multiple Multiple-Services-Credit-Control AVP in CCR-U messages.
endpoint_name must be the endpoint’s name, and an alpha and/or numeric string of 1 through 63 characters in length.
realm realm_name
realm_name must be a string of 1 through 127 characters in length.
The endpoint to configure should be pre-configured. For information on creating and configuring a Diameter endpoint, in the Context Configuration Mode, see the diameter endpoint command.
diameter peer-select peer peer_name [ realm realm_name ] [ secondary-peer secondary_peer_name [ realm realm_name ] ] [ imsi-based start-value imsi_start_value end-value imsi_end_value ]
diameter peer-select peer peer_name [ realm realm_name ] [ secondary-peer secondary_peer_name [ realm realm_name ] ] [ imsi-based { { prefix | suffix } imsi/prefix/suffix_start_value } [ to imsi/prefix/suffix_end_value ] ] [ msisdn-based { { prefix | suffix } msisdn-based/prefix/suffix_start_value } [ to msisdn-based/prefix/suffix_end_value ] ]
no diameter peer-select [ imsi-based { { prefix | suffix } imsi/prefix/suffix_start_value } [ to imsi/prefix/suffix_end_value ] ] | [ msisdn-based { { prefix | suffix } msisdn-based/prefix/suffix_start_value } [ to msisdn-based/prefix/suffix_end_value ] ]
peer peer_name
peer_name must be an alpha and/or numeric string of 1 through 63 characters in length and can contain punctuation characters.
Important: This section applies only to 8.3 and earlier releases.start-value imsi_start_value specifies the start of range in integer value of IMSI, and end-value imsi_end_value specifies the end of range in integer value of IMSI.
imsi-based { { prefix | suffix } imsi/prefix/suffix_start_value } [ to imsi/prefix/suffix_end_value ]
Important: This section applies only to 9.0 and later releases for UMTS deployments.prefix: Specifies the prefix range
suffix: Specifies the suffix range
imsi/prefix/suffix_start_value: Specifies the IMSI/prefix/suffix start value. prefix/suffix must be IMSI prefix/suffix, and must be an integer from 1 through 15 characters in length.
imsi/prefix/suffix_end_value: Specifies the IMSI/prefix/suffix end value. prefix/suffix must be IMSI prefix/suffix, and must be an integer from 1 through 15 characters in length, and must be greater than the start value.
Important: If prefix/suffix is used, the lengths of both start and end prefix/suffix must be equal. If the prefix or suffix keyword is not specified, it will be considered as suffix.msisdn-based { { prefix | suffix } msisdn/prefix/suffix_start_value } [ to msisdn/prefix/suffix_end_value ]
prefix: Specifies the prefix range
suffix: Specifies the suffix range
msisdn/prefix/suffix_start_value: Specifies the MSISDN/prefix/suffix start value. prefix/suffix must be MSISDN prefix/suffix, and must be an integer from 1 through 15 characters in length.
msisdn/prefix/suffix_end_value: Specifies the MSISDN/prefix/suffix end value. prefix/suffix must be MSISDN prefix/suffix, and must be an integer from 1 through 15 characters in length, and must be greater than the start value.
realm realm_name
The realm_name must be an alpha and/or numeric string of 1 through 127 characters in length, and can contain punctuation characters. The realm may typically be a company or service name.
secondary-peer secondary_peer_name
Specifies a name for the secondary host to be used for failover processing. When the route-table does not find an AVAILABLE route, the secondary host performs a failover processing if the diameter session failover command is set.
secondary_peer_name must be an alpha and/or numeric string of 1 through 63 characters in length, and can contain punctuation characters.
If the diameter peer-select command is not configured, and if multiple peers are configured in the endpoint, the available peers configured in the endpoint are automatically chosen in a load-balanced round-robin manner.
The following command configures IMSI-based Diameter credit control peer selection in the IMSI range of 1234567890 to 1234567899:
The following command configures IMSI-based DCCA peer selection with IMSI suffix of 100 through 200:
diameter peer-select peer test_peer realm test_realm secondary-peer test_sec_realm realm test_realm2 imsi-based suffix 100 to 200
diameter pending-timeout duration
duration must be an integer from 1 through 300.
This keyword is deprecated. This can now be managed using the retry-after-tx-expiry and go-offline-after-tx-expiry keywords in the failure-handling command.
If DCCA gets a “no available routes” error before pending-timeout expires, then DCCA tries to send to the secondary host (if one has been configured). If DCCA gets no response and pending-timeout expires, then DCCA either tries the secondary host or gives up. This can now be managed using the failure-handling command.
If routing has failed, i.e., the attempt to the primary host, as well as, the attempt to the secondary host (if that has been configured), then the processing configured by the failure-handling CLI command is performed.
In 12.1 and earlier releases: no-resource-available
In 12.2 and later releases: system-failure
Default: session-start
diameter service-context-id service_context_id
service_context_id must be an alpha and/or numeric string of 1 through 63 characters in length and can contain punctuation characters.
The following command specifies the value version@customer.com is to be sent in the Service-Context-Id AVP in the Diameter CCR message:
diameter service-context-id version@customer.com
Default: Depends on the failure-handling configuration
The failure-handling configuration comes into effect only if diameter session failover is present in the configuration. The failover can be overridden by the server in the response message, and it takes precedence.
Important: This CLI command is applicable ONLY to the dcca-custom8 dictionary. If, for any dictionary other than dcca-custom8, this command is configured with a value other than the default, configuration errors will be indicated in the output of the show configuration errors section active-charging CLI command.initial-request: The default setting is terminate.
update-request: The default setting is retry-and-terminate.
terminate-request: The default setting is retry-and-terminate.
The following command sets the Credit Control Failure Handling behavior for initial request message type to retry-and-terminate:
Default: diameter
pending-traffic-treatment { { { forced-reauth | trigger | validity-expired } drop | pass } | { { noquota | quota-exhausted } buffer | drop | limited-pass volume | pass } }
Default: drop
limited-pass volume
volume specifies the Default Quota size, in bytes, and must be an integer from 1 through 4294967295.
The default pending-traffic-treatment for noquota is drop. The default pending-traffic-treatment noquota command removes any Default Quota limit configured.
This CLI command is different than the failure-handling CLI command, which specifies behavior in the face of an actual timeout or error, as opposed to the behavior while waiting. See also the buffering-limit CLI command in Active Charging Service Configuration Mode.
holding-time holding_time
holding_time must be an integer from 1 through 4000000000.
validity-time validity_time
validity_time must be an integer from 1 through 65535.
quota holding-time 30000
Default: include-packet-causing-trigger
Same as the default quota request-trigger command.
abs_time_value must be an integer from 1 through 86400. To disable this assign 0.
percent percent_value
percent_value must be an integer from 1 through 100.
abs_unit_value must be an integer from 1 through 4000000000. To disable this assign 0.
percent percent_value
percent_value must be an integer from 1 through 100.
quota units-threshold 160400
abs_vol_value must be an integer from 1 through 4000000000. To disable this assign 0.
percent percent_value
percent_value must be an integer from 1 through 100.
quota volume-threshold 160400
Default: cumulative
The following command configures the usage reporting algorithm for RADIUS prepaid using DCCA to relative:
Default: discard-buffered-packet
servers-unreachable { initial-request { continue | terminate [ after-timer-expiry timeout_period ] } | update-request { continue | terminate [ after-quota-expiry | after-timer-expiry timeout_period ] } }
servers-unreachable { behavior-triggers { initial-request | update-request } transport-failure [ response-timeout | tx-expiry ] | initial-request { continue [ { [ after-interim-timetimeout_period ] [ after-interim-volume quota_value ] } server-retries retry_count ] | terminate [ { [ after-interim-time timeout_period ] [ after-interim-volume quota_value ] } server-retries retry_count | after-timer-expiry timeout_period ] } | update-request { continue [ { [ after-interim-time timeout_period ] [ after-interim-volume quota_value ] } server-retries retry_count ] | terminate [ { [ after-interim-time timeout_period ] [ after-interim-volume quota_value ] } server-retries retry_count ] | after-quota-expiry | after-timer-expiry timeout_period ] } }
|
•
|
initial-request: Specifies the behavior when Diameter server(s)/OCS become unreachable during initial session establishment.
|
|
•
|
update-request: Specifies the behavior when Diameter server(s)/OCS become unreachable during mid-session.
|
|
•
|
transport-failure [ response-timeout | tx-expiry ]: Specifies to trigger the behavior either at transport failure, response timeout or at Tx expiry.
|
Important: This section applies only to 12.1 and earlier releases.|
•
|
continue: Specifies to continue call if Diameter server(s) becomes unreachable.
|
|
•
|
terminate [ after-timer-expiry timeout_period ]: Specifies to terminate call if Diameter server(s) becomes unreachable.
|
after-timer-expiry timeout_period: Specifies to terminate call after timeout period expires.
timeout_period specifies the timeout period, in seconds, and must be an integer from 1 through 4294967295.
initial-request { continue [ { [ after-interim-time timeout_period ] [ after-interim-volume quota_value ] } server-retries retry_count ] | terminate [ { [ after-interim-time timeout_period ] [ after-interim-volume quota_value ] } server-retries retry_count ] | after-timer-expiry timeout_period }
Important: This section applies only to 12.2 and later releases.|
•
|
continue: Specifies to continue call if Diameter server(s) becomes unreachable.
|
|
•
|
terminate: Specifies to terminate call if Diameter server(s) becomes unreachable.
|
|
•
|
after-interim-time timeout_period: Specifies to continue or terminate call after the interim timeout period expires.
|
timeout_period specifies the timeout period, in seconds, and must be an integer from 1 through 4294967295.
|
•
|
after-interim-volume quota_value: Specifies to continue or terminate call on exhaustion of the assigned quota.
|
quota_value specifies the volume-based quota value, in bytes, and must be an integer from 1 through 4294967295.
|
•
|
|
•
|
|
•
|
|
•
|
after-timer-expiry timeout_period: Specifies to terminate call after timeout period expires.
|
timeout_period specifies the timeout period, in seconds, and must be an integer from 1 through 4294967295.
|
•
|
server-retries retry_count: Specifies the number of retries that should happen to OCS before allowing the session to terminate/offline.
|
retry_count specifies the retries to OCS, and must be an integer from 0 through 65535. If the value 0 is defined for this keyword, the retry to OCS will not happen instead the configured action will be immediately applied.
Important: This section applies only to 12.1 and earlier releases.|
•
|
continue: Specifies to continue call if Diameter server(s) becomes unreachable.
|
|
•
|
terminate [ after-quota-expiry | after-timer-expiry timeout_period ]: Specifies to terminate call if Diameter server(s) becomes unreachable.
|
|
•
|
after-quota-expiry: Specifies to terminate call on exhaustion of all available quota.
|
|
•
|
after-timer-expiry timeout_period: Specifies to terminate call after timeout period expires.
|
timeout_period specifies the timeout period, in seconds, and must be an integer from 1 through 4294967295.
update-request { continue [ { [ after-interim-time timeout_period ] [ after-interim-volume quota_value ] } server-retries retry_count ] | terminate [ { [ after-interim-time timeout_period ] [ after-interim-volume quota_value ] } server-retries retry_count ] | after-quota-expiry | after-timer-expiry timeout_period ] }
Important: This section applies only to 12.2 and later releases.|
•
|
continue: Specifies to continue call if Diameter server(s) becomes unreachable.
|
|
•
|
terminate: Specifies to terminate call if Diameter server(s) becomes unreachable.
|
|
•
|
after-interim-time timeout_period: Specifies to continue or terminate call after the interim timeout period expires.
|
timeout_period specifies the timeout period, in seconds, and must be an integer from 1 through 4294967295.
|
•
|
after-interim-volume quota_value: Specifies to continue or terminate call on exhaustion of the assigned quota.
|
quota_value specifies the volume-based quota value, in bytes, and must be an integer from 1 through 4294967295.
|
•
|
|
•
|
|
•
|
|
•
|
after-quota-expiry: Specifies to terminate call on exhaustion of all available quota.
|
|
•
|
after-timer-expiry timeout_period: Specifies to terminate call after timeout period expires.
|
timeout_period specifies the timeout period, in seconds, and must be an integer from 1 through 4294967295.
|
•
|
server-retries retry_count: Specifies the number of retries that should happen to OCS before allowing the session to terminate/offline.
|
retry_count specifies the retries to OCS, and must be an integer from 0 through 65535. If the value 0 is defined for this keyword, the retry to OCS will not happen instead the configured action will be immediately applied.
This command works on the same lines as the failure-handling command, which is very generic for each of the xxx-request and applies for CCFH handling during:
For conditions 1 and 2 described above, the failure-handling command will be applied, whereas for condition 3 both failure-handling and/or servers-unreachable commands can be used. This way, the operator has the flexibility to configure CCFH independent of OCS-unreachable feature, that is have two different failure handlings for same request types (as illustrated in the example above.)
Important: Please note that the flexibility to configure CCFH independent of OCS-unreachable feature is applicable only to 12.1 and earlier releases. In 12.2 and later releases, if the servers-unreachable command is configured, it would take precedence over the failure-handling command.If server returns the CC-Failure-Handling AVP, it would apply for conditions 1 and 2 described above. It would also apply for condition 3 if the servers-unreachable CLI is not configured. But, if configured it would take the highest precedence for all Diabase errors scenarios.
Default: roundoff
Use this command to configure reporting usage only for granted quota. On issuing this command, the Used-Service-Unit AVP will report quotas based on grant i.e, only the quotas present in the Granted-Service-Unit AVP.
